IT04133: PCOM: LU3 HOST PRINT VIA TN3270E HANGS IF DATA IS SENT BY WSF COMMAND

Personal Communications 6.0.12
Personal Communications 6.0.13
Personal Communications 6.0.15

APAR status

• Closed as program error.

Error description

• Env:
  z/OS V1.10, CICS TS 3.1
  Personal Communications v6.0.8 / Windows7
  PC TOSHIBA DYNABOOK R731/C 4 core
  
  The customer has a problem about PCOM printer session.
  They changed from SNA connection to TELNET connection. After
  that, when they try to print, printing stops still in spooling
  status.
  
  Before(SNA): CICS-VTAM-OSA-PC-5577 printer.
  After(telnet):CICS-VTAM-TCP/IP(TN3270)-OSA-PC-5577 printer.
  
  Windows Spooler shows "spooling". Even if they press the CANCEL
  button on POCM printer session, print is not canceled.
  
  If the session is disconnected, (Communication --> Disconnect)
  the spool will be printed to the middle.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All PCOM LU3 host print session using TN3270E connectivity   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In a IBM Personal Communications 3270 LU3 host print         *
  * session, the host print data is received with a Write        *
  * Structure Field followed by a Write command with WCC for the *
  * data. This causes the printer session to hang in spooling    *
  * status.                                                      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the printer stops in spooling status, Windows spooler shows
  "spooling". The print job is not cancelled, even if the CANCEL
  button is pressed in the printer session. If the session is
  disconnected (Communication -> Disconnect), the spool is
  partially printed.
  However, the problem does not happen over SNA connectivity.
  
  When the response byte in the TN3270 header is set to
  ALWAYS-RESPONSE (0x02), the emulator session must send a TN3270
  response after processing the data. When the Write Control
  Character (WCC) specifies START_PRINT bit on, response must be
  sent after print data is spooled. So, the timing of sending
  response is different from that of display data. As a result,
  telnet layer of IBM Personal Communications needs to recognize
  the WCC in 3270 data stream. However, the telnet layer was
  referring to WCC incorrectly when 3270 data stream is
  constructed by Write Structured Field and the response was not
  sent to the host. This resulted in session hang.
  
  This problem happens on LU3 host print and LU2 host initiated
  local copy.
  

Problem conclusion

• PCSTLNET.DLL code was corrected to refer to the WCC byte
  correctly and handle the telnet response.
  
  Fix scheduled for PCOM 6.0.12 Refresh Pack
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• PCSTLNET
  

Fix information

• Fixed component name

  PCOMM V5 COMBO-

• Fixed component ID

  5639I7000

Applicable component levels

• R601 PSY

     UP